Apparatus and methods for providing a payment system over a network

ABSTRACT

Apparatus and methods provide an accumulator that processes electronic payments from an employer to a recipient via a network. The payments processed may be, for example, child support payments collected from an employee by the employer. The employer may submit one transaction made up of payments collected from multiple employees bound for multiple recipients and the accumulator may receive, translate, batch, and deliver the payments to the multiple recipients. The accumulator, employers, and recipients may communicate via a network such as the Internet.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication No. 60/260,896 for Method and Apparatus for PaymentProcessing Using Debit-Based Electronic Funds Transfer and DisbursementProcessing Using Addendum-Based Electronic Data Interchange Over aNetwork, which is expressly incorporated herein by reference.Application No. 60/260,896 was filed on Jan. 12, 2001 by Jeffrey F.Kach, John D. Polk, and James K. Selway,

FIELD OF THE INVENTION

The present invention relates to apparatus and methods for providing apayment system over a network. In particular, the present inventionrelates to apparatus and methods for providing a payment system over anetwork for multiple employers to make multiple payments to multiplerecipients.

BACKGROUND OF THE INVENTION

Electronic payments are faster, less expensive, more secure, and moreefficient than check-based payments. For example, the direct depositarrangement between employers and banks provides a fast and secureelectronic alternative to traditional paper paychecks for the payment ofemployees. Under the direct deposit arrangement, an employee's paycheckis electronically deposited from the employer's account to theemployee's account, thus saving time and expense while providing atransaction that is convenient for the employer and the employee.

Employers may fulfill payment obligations on behalf of their employeesby collecting funds, such as taxes or child support payments, andremitting the funds to appropriate recipients. In the case of taxpayments, the recipient may be, for example, a federal or state entity.In the case of child support payments, the recipient may be, forexample, an intermediary such as a state agency charged withdistributing child support payments. Often, the recipient may differfrom employee to employee. For example, an employer, such as a nationalcorporation, may collect child support payments from employees thatreside and owe child support in different states. The employer musttherefore process payments for many different recipients, a confusingand time-consuming process.

To ease the submission of payments collected by an employer, there is aneed for a system to collect and process payments from multipleemployees for multiple recipients in an electronic manner. However, manyobstacles prohibit electronic payment processing on a state or nationalbasis. First, a single employer may collect payments, such as childsupport payments, for recipients in several different states. Second, inthe context of child support payments, each state may have differentrules that govern the information employers must provide with payments.State agencies that oversee the payment process require processinginformation that may differ from state to state. Third, electronicpayment processing requires new technology. Many employers are unable toafford purchasing or developing new technology for electronic paymentprocessing.

Despite these obstacles, there is a need for an electronic paymentprocessing system that accommodates the requirements of multipleemployees for multiple recipients and that does not require aninvestment in new technology and/or equipment. Furthermore, there is aneed for an electronic payment system whereby the employer may initiatetransactions over a network, such as the Internet, with a singleprocessing entity rather than submitting payments directly to multiplerecipients.

SUMMARY OF THE INVENTION

A system consistent with the present invention may be accessed by anemployer over a network such as the Internet. The employer may use sucha system to submit payments collected from employees to a recipient,such as a state agency responsible for delivering a child supportpayment. Consistent with the present invention, the recipient may or maynot be a government entity. For example, a state may hire a privatecompany to collect and disburse payments such as child support payments.

Consistent with the present invention, an employer may interact with anaccumulator via the network to create an employee withholding profilefor each employee for which the employer withholds a payment, such as achild support payment. Employers may use the system for any type ofemployee, such as employees paid monthly, weekly, or bi-weekly. Tosubmit a payment, an employer may provide data regarding the employeeand the payment to the accumulator via the Internet. The data mayinclude information such as the employee's name, social security number,case number or account number with the payment recipient, the amountwithheld, the date of the withholding, and whether the employee hasmedical insurance. The data provided may vary from recipient torecipient. For example, an agency in one state may require child supportpayers to carry medical insurance while an agency in another state maynot.

When the accumulator collects information from an employer for employeeswith different recipients, the accumulator may filter and/or format thedata according to each recipient's requirements. In this way, theemployer may submit one set of data that is customized for multiplerecipients by the accumulator. This greatly simplifies the task of anemployer with employees in multiple states.

To process a payment, the accumulator may receive a payment from anemployer and pass the payment to an Automated Clearinghouse (ACH) orother electronic payment processor. The ACH may pass the payment to theemployer's bank as a debit, where the money is taken electronically froman account of the employer. When the money is collected from theemployer's bank, the ACH may pass a corresponding credit back to theaccumulator, which the accumulator may then submit to the recipient. Thepayment may be processed using, for example, addendum-based electronicdata interchange.

Consistent with the present invention, an employer may submit onetransaction made up of payments collected from multiple employees boundfor multiple recipients and the accumulator may process a singletransaction to the employer's bank. The accumulator may then break upthe single transaction, grouping the payments by recipient. The dataabout a payment may be filtered and/or formatted according to itsrecipient, and the data and a credit may be sent to the appropriaterecipient. In this way, apparatus and methods consistent with thepresent invention advantageously enable an employer to submit paymentsfor multiple employees and/or multiple recipients to a singleaccumulator via a network. The accumulator receives the payments, groupsand translates them by recipient, and delivers them to ensure accurateand efficient distribution of all payments.

Additional advantages of the invention will be set forth in part in thedescription which follows, and in part will be obvious from thedescription, or may be learned by practice of the invention. The objectsand advantages of the invention will be realized and attained by meansof the elements and combinations particularly pointed out in theappended claims.

It is to be understood that both the foregoing general description andthe following detailed description are exemplary and explanatory onlyand are not restrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments of theinvention and together with the description, serve to explain theprinciples of the invention.

In the drawings:

FIG. 1 is a block diagram of a system, consistent with one embodiment ofthe present invention;

FIG. 2 is another block diagram of a system, consistent with oneembodiment of the present invention;

FIG. 3 is a more detailed block diagram of a system, consistent with oneembodiment of the present invention;

FIG. 4 is a block diagram of an accumulator, consistent with oneembodiment of the present invention;

FIG. 5 is a block diagram of accumulator in greater detail, consistentwith one embodiment of the present invention;

FIG. 6 is a block diagram of accumulator agency in greater detail,consistent with one embodiment of the present invention;

FIG. 7 is a flowchart of processing performed by an employerapplication, consistent with one embodiment of the present invention;

FIG. 8 is a flowchart of an embodiment of an employer registrationprocess, consistent with one embodiment of the present invention;

FIG. 9 is a flowchart of an embodiment of a log in process, consistentwith one embodiment of the present invention;

FIG. 10 is a flowchart of an embodiment of an add bank accountprocedure, consistent with one embodiment of the present invention;

FIG. 11 is a flowchart of an embodiment of a user set up procedure,consistent with one embodiment of the present invention;

FIG. 12 is a flowchart of an embodiment of a change password procedure,consistent with one embodiment of the present invention;

FIG. 13 is a flowchart of an embodiment of a payment set up procedure,consistent with one embodiment of the present invention;

FIG. 14 is a flowchart of an embodiment of a payment profile set upprocedure, consistent with one embodiment of the present invention;

FIG. 15 is a flowchart of an embodiment of an employee detail set upprocedure, consistent with one embodiment of the present invention;

FIG. 16 is a flowchart of an embodiment of an add employee procedure,consistent with one embodiment of the present invention;

FIG. 17 is a flowchart of an embodiment of a FIPS code look upprocedure, consistent with one embodiment of the present invention;

FIG. 18A is a sample welcome interface, consistent with one embodimentof the present invention;

FIG. 18B is a sample employer registration interface, consistent withone embodiment of the present invention;

FIG. 18C is a sample registration verification interface, consistentwith one embodiment of the present invention;

FIG. 18D is a sample terms and conditions interface, consistent with oneembodiment of the present invention;

FIG. 18E is a sample registration confirmation interface, consistentwith one embodiment of the present invention;

FIG. 18F is a sample account home interface, consistent with oneembodiment of the present invention;

FIG. 18G is a sample add bank account detail interface, consistent withone embodiment of the present invention;

FIG. 18H is a sample bank account detail interface, consistent with oneembodiment of the present invention;

FIG. 18I is a sample verify bank account information interface,consistent with one embodiment of the present invention;

FIG. 18J is a sample user list interface, consistent with one embodimentof the present invention;

FIG. 18K is a sample of a user detail interface, consistent with oneembodiment of the present invention;

FIG. 18L is a sample change password interface, consistent with oneembodiment of the present invention;

FIG. 18M is a sample create payment home interface, consistent with oneembodiment of the present invention;

FIG. 18N is a sample payment detail interface, consistent with oneembodiment of the present invention;

FIG. 18O is a sample employee list interface, consistent with oneembodiment of the present invention;

FIG. 18P is a sample payment verification interface, consistent with oneembodiment of the present invention;

FIG. 18Q is a sample payment confirmation interface, consistent with oneembodiment of the present invention;

FIG. 18R is a sample payment profile list interface, consistent with oneembodiment of the present invention;

FIG. 18S is a sample payment profile detail interface, consistent withone embodiment of the present invention;

FIG. 18T is a sample employee detail interface, consistent with oneembodiment of the present invention;

FIG. 18U is a sample FIPS lookup table interface, consistent with oneembodiment of the present invention;

FIG. 18V is a sample reports interface, consistent with one embodimentof the present invention;

FIG. 18W is a sample payment transaction report, consistent with oneembodiment of the present invention;

FIG. 18X is a sample payment profile report, consistent with oneembodiment of the present invention;

FIG. 18Y is a sample employee payment history report, consistent withone embodiment of the present invention;

FIG. 19 is a flow chart of processing performed by an administratorapplication, consistent with one embodiment of the present invention;

FIG. 20 is a flow chart of an embodiment of a user permissions updateprocedure, consistent with one embodiment of the present invention;

FIG. 21 is a flow chart of an embodiment of a company information updateprocedure, consistent with one embodiment of the present invention;

FIG. 22 is a flow chart of an embodiment of a bank account informationupdate procedure, consistent with one embodiment of the presentinvention;

FIGS. 23A and 23B are flow charts of an embodiment of a returns handlingprocedure, consistent with one embodiment of the present invention;

FIG. 24 is a flowchart of an embodiment of a credit batch handlingprocedure, consistent with one embodiment of the present invention;

FIG. 25 is a flowchart of an embodiment of a batch processing procedure,consistent with one embodiment of the present invention;

FIG. 26A is a sample company list interface, consistent with oneembodiment of the present invention;

FIG. 26B is a sample company search interface, consistent with oneembodiment of the present invention;

FIG. 26C is a sample company detail interface, consistent with oneembodiment of the present invention;

FIG. 26D is a sample bank account list interface, consistent with oneembodiment of the present invention;

FIG. 26E is a sample bank account detail interface, consistent with oneembodiment of the present invention;

FIG. 26F is a sample returns interface, consistent with one embodimentof the present invention;

FIG. 26G is a sample disable company interface, consistent with oneembodiment of the present invention;

FIG. 26H is a sample batch status interface, consistent with oneembodiment of the present invention;

FIG. 26I is a sample batch information interface, consistent with oneembodiment of the present invention;

FIG. 26J is a sample debit batch information interface, consistent withone embodiment of the present invention;

FIG. 26K is a sample credit batch detail interface, consistent with oneembodiment of the present invention;

FIG. 26L is a sample reports menu, consistent with one embodiment of thepresent invention;

FIG. 26M is a sample batch summary report, consistent with oneembodiment of the present invention;

FIG. 26N is a sample payment submittal summary report, consistent withone embodiment of the present invention;

FIG. 26O is a sample SDU credit submittal summary report, consistentwith one embodiment of the present invention;

FIG. 26P is a sample employer payment returns report, consistent withone embodiment of the present invention;

FIG. 27 is a block diagram of a system for processing payments formultiple states, consistent with one embodiment of the presentinvention;

FIG. 28 is another block diagram of a system for processing payments tomultiple states, consistent with one embodiment of the presentinvention;

FIG. 29 depicts a series of templates consistent with one embodiment ofthe present invention; and

FIG. 30 shows a plurality of delivery methods, consistent with oneembodiment of the present invention.

DETAILED DESCRIPTION

Reference will now be made in detail to the exemplary embodiments of theinvention, examples of which are illustrated in the accompanyingdrawings. Wherever possible, the same reference numbers will be usedthroughout the drawings to refer to the same or like parts.

FIG. 1 is a block diagram of a system, consistent with one embodiment ofthe present invention. An employer 102 may access an accumulator 104 viaa network 106, such as the Internet. To do so, employer 102 may use, forexample, an Internet browser such Microsoft Internet Explorer™ orNetscape Navigator™. Employer 102 collects payments from one or moreemployees 108, for example, by withholding an amount from an employee'spaycheck. This withholding could be carried out, for example, pursuantto a court-issued child support order. Using methods and apparatusconsistent with the present invention, accumulator 104 processes thepayments collected by employer 102 and delivers them to a recipient 110.In the child support context, recipient 110 may be a state disbursementunit (SDU) or other agency responsible for processing child supportpayments. Recipient 110 may be a governmental entity or anongovernmental entity, e.g., a commercial entity. In one embodiment(not shown) accumulator 104 and recipient 110 may be combined into oneentity, accumulator/recipient 112. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 2 is another block diagram of a system, consistent with oneembodiment of the present invention. As shown in FIG. 2, employer 102passes payment instructions to accumulator 104. The payment instructionsmay indicate, for example, that employer 102 has collected a paymentfrom an employee or a plurality of employees. Accumulator 104 generatesa debit and sends it to an accumulator bank 202. Accumulator bank 202may pass the debit to an Automated Clearinghouse (ACH) 204. ACH 204 maybe, for example, a known clearinghouse for processing electronicpayments. ACH 204 then issues the debit against an employer's bank 206to withdraw the money for the payment. ACH 204 may also return anoffsetting credit to accumulator bank 202 for the benefit of accumulator104. The credit may then be delivered by accumulator 104 to a recipient,such as recipient 110 (not shown). It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 3 is a more detailed block diagram of a system, consistent with oneembodiment of the present invention. In particular, FIG. 3 depictsemployer 102 using network 106 to access accumulator 104. In thisembodiment, accumulator 104 includes an operations desk 302 to generatereports, for example, reports used by an accounting and finance desk304. Accumulator 104 may also include a delivery module 306 fordelivering, for example, data output and debit processing. For example,delivery module 306 may be used by accumulator 104 to transmit data toSDU 110 and to send a debit to accumulator bank 202. It should be notedthat other embodiments are possible, consistent with the presentinvention.

Accumulator bank 202 may pass the debit to employer's bank 206. Asdescribed above, accumulator bank 202 and employer's bank 206 may useACH 204 (not shown) as a trusted third party processor. Accumulator bank202 may then pass an offsetting credit to SDU bank 308, also via SDU110. Although accumulator 104, operations desk 302, accounting andfinance desk 304, and delivery module 306 are depicted as separate inFIG. 3, one skilled in the art will recognize that these elements mayall be combined in accumulator 104. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 4 is a block diagram of accumulator 104, consistent with oneembodiment of the present invention. Accumulator 104 includes employerapplication 402, administrator application 404, payment processor 406,communication manager 408, and validation processor 410. Employerapplication 402 may facilitate interaction with employer 102 toimplement apparatus and methods consistent with the present invention.Employer application 402 is described in greater detail below withreference to FIGS. 7-18. Administrator application 404 may enable anadministrator at accumulator 104 to administer and maintain employerapplication 402, payment processor 406, communications manager 408, andvalidation processor 410. Administrator application 404 is described ingreater detail below with reference to FIGS. 19-26.

Payment processor 406 may process debits and credits for accumulator104. Communication manager 408 may manage communications betweenaccumulator 104 and, for example, employer 102, recipient 110, and anyother entities available via network 106. Validation processor 410 maybe used to validate instructions and information received from employer102 and a recipient 110. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 5 is a block diagram of accumulator 104 in greater detail,consistent with one embodiment of the present invention. As shown inFIG. 5, employer application 402, administrator application 404, paymentprocessor 406, communication manager 408, and validation processor 410all have access to a web server 502 and a payment database 504. Webserver 502 may include graphic user interfaces displayed via employerapplication 402 and administrator application 404 to provide a web-basedaccumulator. Accumulator 104 may also include a database server 506 andan FTP server 508. Database server 506 may maintain many databases, forexample payment database 504, profiles database 510, registrationdatabase 512, validation database 514, and users database 516. AlthoughFIG. 5 depicts several separate databases, one skilled in the art willrecognize that a single accumulator database may be used. FTP server 508may utilize file transfer protocol (FTP), for example, to assistcommunication manager 408 in managing communications for accumulator104. It should be noted that other embodiments are possible, consistentwith the present invention.

FIG. 6 is a block diagram of accumulator agency 104 in greater detail,consistent with one embodiment of the present invention. Employerapplication 402 stores user information, employer account information,payment profiles, and other data in accumulator database 602.Accumulator database 602 may include, for example, profiles database510, registration database 512, validation database 514, and usersdatabase 516. Although accumulator database 602 and payment database 504are depicted as separate in FIG. 6, one skilled in the art willrecognize that they could be combined into a single database. Userinformation may be stored, for example, in user database 516. Employeraccount information may be stored, for example, in registration database512. Payment profile information may be stored, for example, in profiledatabase 510.

Validation processor 410 may receive validation information from SDU 110to enable accumulator 104 to verify information received from employer102. For example, validation processor 410 may verify that an employeeof employer 102 is in fact liable for the payment submitted by employer102. Validation processor 410 may store validation information, forexample, in validation database 514, which may be located in accumulatordatabase 602.

Administrator application 404 enables an administrator to interact withaccumulator 104. For example, administration application 404 may enablea user to retrieve stored payment data from payment processor 406 toinitiate a manual or automatic reconciliation process. Administratorapplication 404 may also receive messages, such as error messages orservice requests, from employer application 402. Payment processor 406may retrieve payment information stored by employer application 402 inpayment database 504. Payment database 504 may be used by employerapplication 402 to create payments and submit payments.

Communication manager 408 may access payment database 504, for example,to retrieve debit or credit information and deliver it to accumulatorbank 202. Communication manager 408 may deliver the debit and/or creditinformation to accumulator bank 202 using, for example, file transferprotocol (FTP). It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 7 is a flowchart of processing performed by employer application402, consistent with one embodiment of the present invention. To carryout the steps shown in FIG. 7, employer application 402 may present aseries of graphical user interfaces to the employer using web server502. In this way, employers can interact with a website to communicatewith accumulator 104. As shown in FIG. 7, the first time an employervisits the accumulator website (step 702), the employer is prompted toregister (step 704). An embodiment of the employer registration processis described below with reference to FIG. 8. If the employer has alreadybeen to the accumulator website, the employer is prompted to log in(step 706). An embodiment of the log in process is described below withreference to FIG. 9.

Once logged in, the employer can make several different selections forcommunicating with accumulator 104. These choices may be presented tothe employer, for example, as a series of links on a web page. If theemployer selects add bank account (step 708), then employer application402 implements an add bank account information procedure (step 710). Anembodiment of the add bank account information procedure is describedbelow with reference to FIG. 10.

If the employer selects user set up (step 712), then employerapplication 402 follows a user set up procedure (step 714). Anembodiment of the user set up procedure is described below withreference to FIG. 11. If the employer selects change password (step716), then employer application 402 implements a change passwordprocedure (step 718). An embodiment of the change password procedure isdescribed below with reference to FIG. 12. If the employer selectspayment set up (step 720), then employer application 402 performs apayment set up procedure (step 722). An embodiment of the payment set upprocedure is described below with reference to FIG. 13.

If the employer selects payment profile set up (step 724), then theemployer application 402 performs a payment profile set up procedure(step 726). An embodiment of the payment profile set up procedure isdescribed below with reference to FIG. 14. If the employer selectsemployee detail set up (step 728), then employer application 402performs an employee detail set up procedure (step 730). An embodimentof the employee detail set up procedure is described below in referenceto FIG. 15. If the employer selects add employee (step 729), thenemployer application 402 performs an add employee procedure (step 731).An embodiment of the add employee procedure is described below withreference to FIG. 16. If the employer selects look up FIPS code (step732), then employer application 402 performs an FIPS code look upprocedure (step 734). An embodiment of the FIPS code look up procedureis described below with reference to FIG. 17. Finally, the employer maychoose to log out (step 736). It should be noted that other embodimentsare possible, consistent with the present invention.

FIG. 8 is a flowchart of an embodiment of an employer registrationprocess, consistent with one embodiment of the present invention. Theprocess begins when the employer navigates to the accumulator website(step 802). FIG. 18A includes a sample welcome interface that may bepresented to the employer. When the employer chooses to register, e.g.,by selecting a “register now” button (step 804), a company registrationform interface is displayed (step 806). FIG. 18B includes a sample ofcompany registration form interface. When the employer completes thecompany registration form and chooses “continue” (step 808), employerapplication 402 checks to see if the form is completed correctly (step810). If the form is not completed correctly, employer application 402advises the employer of any missing or bad data (step 812). If the formis completed correctly, then a registration verification interface isdisplayed (step 814). FIG. 18C includes a sample registrationverification interface. When the employer verifies the information onthe registration verification interface and chooses “continue” (step816), a terms and conditions interface is displayed (step 818). FIG. 18Dincludes a sample terms and conditions interface. When the user chooses“accept” (step 820), employer application 402 saves the registrationinformation in the accumulator database (step 822). This information maybe stored, for example, in registration database 512. Employerapplication 402 assigns an account number to the employer (step 824) andgenerates a password for a primary user at the employer (step 826). Ane-mail is sent to the employer's address advising that the registrationis complete (step 828) and a registration confirmation interface isdisplayed (step 830). FIG. 18E includes a sample registrationconformation interface. In one embodiment of the present invention, theemployer may complete the registration process by printing the completedregistration form, signing it, and mailing it to an administrativeoffice with a voided check to authenticate the employer's identityand/or bank account information.

After receiving a user ID and a password, the employer may log onto theweb-check system. Once the employer logs onto the system, the employermay be prompted to enter a Federal Employer Identification Number(FEIN), an user ID and an initial temporary password. Subsequent accessto the system by the employer may allow the employer to select aprofile, change a profile, and to make payments by entering theappropriate amounts and submitting the payments to the system. It shouldbe noted that other embodiments are possible, consistent with thepresent invention.

FIG. 9 is a flowchart of an embodiment of a log-in process, consistentwith one embodiment of the present invention. When an employer navigatesto the accumulator website (step 902), the employer may enter the userID and password into a welcome interface to sign in, e.g., by choosing a“sign in” button (step 904). For example, the user ID and password maybe entered in an “already registered” box on the welcome interface.Employer application 402 determines whether the user ID and passwordentered match a stored user ID and password (step 906). If the entereduser ID and password match a stored user ID and password, then anaccount home interface is displayed (step 908). FIG. 18F includes asample account home interface. If the entered user ID and password donot match a stored user ID and password, then employer application 402determines whether the employer has made three attempts to log in to theaccumulator website (step 910). If the employer has not made threeattempts to log in, then a message is displayed informing the employerthat the password or identification information is incorrect andprompting the employer to try again (step 912). The employer is thengiven another chance to enter the user ID and password (step 904). Ifthe user has three unsuccessful attempts at signing in, then a messageis displayed telling the user that they must be properly registered inorder to use the website and instructing them to register now to beginthat process. The message may provide a toll free number to call formore information (step 914). One of skilled in the art will recognizethat the number of attempts before this message is displayed may begreater or fewer than three consistent with the present invention. Itshould be noted that other embodiments are possible, consistent with thepresent invention.

FIG. 10 is a flowchart of an embodiment of an add bank accountprocedure, consistent with one embodiment of the present invention.Using this process, an employer 102 may add a new bank account to itsinformation stored at accumulator 104. FIG. 18G contains a sample addbank account list interface. When an add bank account list interface isdisplayed (step 1002), the employer may choose to add a new bankaccount, for example, by choosing a “new bank account” button (step1004). When the employer chooses to add a new bank account, a bankaccount detail interface is displayed (step 1006). FIG. 18H includes asample bank account detail interface. The employer may use the bankaccount detail interface to provide information about a new bankaccount. The employer may indicate that he is finished, for example, bychoosing a “continue” button (step 1008).

A verify bank account information interface is displayed (step 1010) toenable the employer to view the information just entered. FIG. 18Iincludes a sample verify bank account information interface. When anemployer verifies the information and chooses to continue, e.g., bychoosing a “continue” button (step 1012), then employer application 402stores the bank account detail information in the accumulator database(step 1014). The bank account detail information may be stored, forexample, in registration database 512 or payment database 504. It shouldbe noted that other embodiments are possible, consistent with thepresent invention.

FIG. 11 is a flowchart of an embodiment of a user set up procedure,consistent with one embodiment of the present invention. Using thisprocess, an employer 102 may add or edit a user that is authorized toact on the employer's behalf. During the employer registration processdescribed above, the employer is prompted to provide the name and otherinformation for a primary user. This primary user may add and/or editadditional users with the assistance of a user list interface. FIG. 18Jincludes a sample user list interface. On the user list interface, theprimary user may choose an “add user” button or select a user ID linkcorresponding to a specific user (step 1102). In response, a user detailinterface is displayed (step 1104). FIG. 18K includes a sample userdetail interface. The primary user may enter user detail information oruser permission detail and choose “save” (step 1106). Employerapplication 402 determines whether the entered information includes achange to an existing user ID and/or password (step 1108). If the userinformation does not represent a change to an existing user ID and/orpassword, then employer application 402 determines whether an existinguser has been changed to active status (step 1110). If not, then anupdated user list interface is displayed (step 1112). If the userinformation does represent a change to an existing user ID and/orpassword (step 1108), then a new password is generated for the user(step 1114), and a sign in information e-mail is sent to the user (step1116). Similarly, if an existing user is changed to active status (step1110), then a new password is generated (step 1114) and a sign ininformation e-mail is sent (step 1116). It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 12 is a flowchart of an embodiment of a change password procedureconsistent with the present invention. Using this process, a registereduser may change his or her password. When a user logs in to the website(step 1202), the user may select change password from the main accountinterface (step 1204). A change password interface is displayed (step1206). FIG. 18L includes a sample change password interface. The user isprompted to enter the new password twice before choosing “save” (step1208). Employer application 402 determines whether the new password isthe same as the old password (step 1210). If they are the same, amessage is sent to the user that the new password must be different fromthe old password (step 1212). If the new password and old password aredifferent, the user's profile is updated with the new password (step1214), and a message is sent to the user confirming the password change(step 1216). The updated user profile may be stored, for example, inuser database 516. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 13 is a flowchart of an embodiment of a payment set up procedureconsistent with the present invention. Using this process, a user atemployer 102 may create and submit payments using accumulator 104. Whena user selects create payment from the main screen after logging in(step 1302), a create payment home interface is displayed (step 1304).FIG. 18M includes a sample create payment home interface. The user maycreate a one time payment or may use an existing payment profile. Tosubmit payments for multiple employees, an employer may create a paymentprofile. When creating a payment profile, the employer may enter dataconcerning the employees, including assigning an employee to a payrollbased on the employee's payroll dates, for example. As each employee isadded to a profile, validation processor 410 may validate the employee'sname and other information. Once a payment profile is created, anemployer may create a payment or debit for the employees as a group.

To submit a payment using a payment profile, the user may select aprofile name from a drop-down list containing available payment profilesand choose “continue” (step 1306). A payment detail interfacecorresponding to the selected profile name is displayed (step 1308).FIG. 18N includes a sample payment detail interface. The user mayprovide payment details, such as the date funds are withheld from theemployees in the profile, and choose “continue” (step 1310). An employeelist interface containing a list of employees related to the selectedpayment profile is then displayed (step 1312). FIG. 18O contains asample employee list interface.

The user may modify employee withholding information if necessary usingthe employee list interface and choose “continue” (step 1314). A paymentverification interface is then displayed to enable the user to view thepayment information (step 1316). FIG. 18P includes a sample paymentverification interface. When the user verifies the payment informationand chooses “submit payment” (step 1318), employer application 402stores the payment information to payment database 504 (step 1320) and apayment confirmation interface is displayed (step 1322). FIG. 18Qincludes a sample payment confirmation interface. It should be notedthat other embodiments are possible, consistent with the presentinvention.

FIG. 14 is a flowchart of an embodiment of a payment profile set upprocedure, consistent with one embodiment of the present invention. Whena user selects “payment profiles” from the main screen after logging in(step 1402), a payment profile home interface is displayed (step 1404).FIG. 18R includes a sample payment profile home interface. The user mayuse the payment profile home interface to locate the desired paymentprofile and may select it by choosing a profile name text link (step1406). A payment profile detail interface is displayed (step 1408). FIG.18S includes a sample payment profile detail interface. The user mayenter new payment profile information or edit existing payment profiledetail information on the payment profile detail interface and choose a“save and update” button when finished (step 1410). The payment profileinformation is stored, for example, in payment database 504 (step 1412).It should be noted that other embodiments are possible, consistent withthe present invention.

FIG. 15 is a flowchart of an embodiment of an employee detail set upprocedure, consistent with one embodiment of the present invention.Using this process, a user may add, edit, or delete employeeinformation. When a user chooses an employee name text link on thepayment profile detail interface (step 1502), an employee detailinterface is displayed (step 1504). FIG. 18T contains a sample employeedetail interface. The user may edit employee detail information, e.g.,name, social security number, etc., and choose “save” (step 1506).Employer application 1402 stores the employee case detail informationin, for example, payment database 504 (step 1508) and an updated paymentprofile detail interface is displayed (step 1510). It should be notedthat other embodiments are possible, consistent with the presentinvention.

FIG. 16 is a flowchart of an embodiment of an add employee procedure,consistent with one embodiment of the present invention. Using thisprocess, a user may add an employee using an “add employee” button onthe employee list interface. When the user selects the “add employee”button (step 1602), an employee detail interface is displayed (step1604). FIG. 18T includes a sample employee detail interface. Using theemployee detail interface, the user may provide data about a newemployee. When the user completes the employee information and chooses“save” (step 1606), employer application 402 stores the employee detailinformation, for example, in payment database 504 (step 1608). Anupdated payment detail interface is then displayed (step 1610). Itshould be noted that other embodiments are possible, consistent with thepresent invention.

FIG. 17 is a flowchart of an embodiment of a FIPS code look upprocedure, consistent with one embodiment of the present invention.Using this process, a user may look up the Federal InformationProcessing (FIPS) code corresponding to an employee. A FIPS code may beassigned, for example, to each county in a state to provide uniforminformation processing. When a user chooses a “FIPS look up” button onthe add employee case detail interface (step 1702), an FIPS look uptable is displayed (step 1704). FIG. 18U includes a sample FIPS look uptable interface. Using the FIPS look up table, the user may locate thecounty name corresponding to the new employee. The user may select aFIPS code and select “submit” (step 1706). The FIPS look up table windowmay be closed (step 1708), and the FIPS field on the employee casedetail interface will be populated with the selected FIPS code (step1710). The FIPS look up table advantageously enables a user who knows acounty name to determine the corresponding FIPS county code withouthaving to memorize county codes. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18A is a sample welcome interface, consistent with one embodimentof the present invention. The welcome interface shown in FIG. 18A may bedisplayed by employer application 402 when an employer navigates to awebsite for interacting with accumulator 104. The welcome interface mayinclude a state information box 18A02 with a drop-down list 18A04containing a list of the states compatible with accumulator 104 and a“Go” button 18A06 that opens a new window with the selected state'sinformation page.

The welcome interface may include an “Already Registered” box 18A08 witha text box for a user ID 18A10 and a password 18A12. The user ID and thepassword may be of alphanumeric format, for example. Consistent with thepresent invention, the password 18A12 may be displayed as encrypted whenit is entered. The “Already Registered” box may also include a “Sign In”button 18A14 that will validate the employer's user ID and password, asdescribed above with reference to FIG. 9.

The welcome interface may also include a “Forgotten Your Password” boxwith a text box for a user ID 18A16 and a “Send It” button 18A18. “SendIt” button 18A18 may match the entered user ID with stored user accountinformation including an e-mail address. If a match is found, thewebsite may e-mail the password to the employer at the stored e-mailaccount. The welcome page may also include a “register now” link 18A20that enables a company to register for the website and a “generalinformation” link to 18A22 to enable an employer to view generalinformation. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 18B is a sample employer registration interface, consistent withone embodiment of the present invention. An employer registrationinterface can be used to gather information from the employer about theemployer and a primary user authorized to act on the employee's behalf.The information can include, for example, a Federal EmployeeIdentification Number (FEIN) 18B02, a company name and street address18B04, a company city and state 18B06, a ZIP code 18B08, and a ZIP codeplus 4 number 18B10. Information about the primary user may include theprimary user's first name and last name 18B12, a primary user phonenumber 18B14, user ID 18B16, and e-mail address 18B18. The registrationinterface may include a “Continue” button 18B20 that enables an employerto continue with the registration process, as described in FIG. 8 above.The employer registration interface may also include an indicator of thestep of the registration process 18B22, a “Cancel Registration” button18B24, and a “Clear Form” button 18B26. “Cancel Registration” button18B24 allows an employer to abandon the registration process and theinterface. The “Clear Form” button 18B26 clears all the form fields ofcontents and displays the employer registration interface with blankfields. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 18C is a sample registration verification interface, consistentwith one embodiment of the present invention. This interface includescompany information and primary user information 18C02. Companyinformation and primary user information 18C02 may be displayed in aread only format to allow an employer to verify the information enteredinto the employer registration interface. The registration verificationinterface may also include a “Continue” button 18C04 that enables theuser to continue with the registration process once the registrationinformation is verified. The registration verification interface mayalso include an indicator of the step of the registration process 18C06as well as a “Make Changes” button 18C08. “Make Changes” button 18C08may return the employer to the employer registration interface to enablethe user to change the entered information. It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 18D is a sample terms and conditions interface, consistent with oneembodiment of the present invention. This interface may include theterms and conditions of using the website. The terms and conditionsinterface may include an “Agree” button 18D02 and a “Cancel” button18D04. “Agree” button 18D02 saves the employer information to a databaseand creates the employer's account. “Agree” button 18D02 can alsotrigger an account information e-mail to be sent to the employer.“Cancel” button 18D04 abandons the interface, saving no registrationinformation. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 18E is a sample registration confirmation interface, consistentwith one embodiment of the present invention. This registrationconfirmation interface may be displayed, for example, once the employerhas agreed to the terms and conditions. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18F is a sample account home interface, consistent with oneembodiment of the present invention. The account home interface mayinclude, for example, a read only summary 18F02 of users' transactions.Read only summary 18F02 may include, for example, a company name, username, last sign in date, last payment date, last payment amount, andlast payment number of employees. The last sign in date and last paymentdate 18F04 may be in a month/day/year format and may include the hours,minutes, and an am/pm indicator. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18G is a sample add bank account detail interface, consistent withone embodiment of the present invention. The add bank account detailinterface may include a new bank account button 18G02 to enable a userto add a bank account as explained in FIG. 10. When a user chooses the“New Bank Account” button, a bank account detail interface is displayed,as described below with reference to FIG. 18H. The add bank accountdetail interface may include, for example, a routing number, a bankname, an account number, an account type, a maximum daily withdrawalamount, a default bank indicator, and an action button with an “E” or a“D”, representing “edit” or “delete.” “Edit” button 18G04 displays andpopulates the bank account detail interface for the selected bankaccount. “Delete” button 18G06 removes the selected bank account fromthe bank account list unless it is related to a payment profile. If thebank account is related to a payment profile, the user will receive amessage that the bank account cannot be deleted without first editingthe corresponding payment profile. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18H is a sample bank account detail interface, consistent with oneembodiment of the present invention. The bank account detail interfacemay include, for example, a routing transit number 18H02, an accountnumber 18H04, an account type 18H06, a maximum daily withdrawal amount18H08, and a default account indicator 18H10. Routing transmit number18H02 and account number 18H04 may be, for example, numbers assigned tothe account by the bank. Account type 18H06 may be, for example, adrop-down list from which a user may select either checking or savings.Maximum daily withdrawal amount 18H08 may be, for example, an amount setby the bank to limit daily withdrawals. Default account indicator 18H10allows the user to indicate if they want to designate the bank accountas a default account to be used when a specific account is notdesignated. The bank account detail interface may also include a“Continue” button 18H12 that may perform routing number validation anddisplay a verify bank account information interface. The bank accountdetail interface may also include a “Cancel” button 18H14 that abandonsthe interface without saving any information. It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 18I is a sample verify bank account information interface,consistent with one embodiment of the present invention. The verify bankaccount information interface may include a bank name 18I02 in read onlyformat. The bank name 18I02 may be obtained, for example, by looking upthe routing transit number in a table, such as a Thomson table. Theverify bank account information interface may also include read onlyvalues 18I04, such as a routing transit number, account number, accounttype, and maximum daily withdrawal amount. Read only values 18I04 may betaken from the data entered into the bank account detail interface. Theverify bank account information interface may also include a defaultaccount identifier 18I06, a “Continue” button 18I08 that saves the bankaccount details, and a “Cancel” button 18I10 that abandons the interfacewithout saving any information. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18J is a sample user list interface, consistent with one embodimentof the present invention. The user list interface may include a list18J02 of the users authorized to act on behalf of the employer. List18J02 may include all users except for the primary user or list 18J02may include the primary user also. The user list interface may includean “Add User” button 18J04 to enable a primary user to add other users.The user list interface may also include user ID text links 18J06 thatlink to the respective user detail interface. On user list 18J02,selecting a column header 18J08 will sort the payment list by the datain that column. User list interface may also include a “Delete SelectedUsers” button 18J10 to remove selected users from the user list. Theprimary user can indicate which users to remove using check boxes 18J12.User list interface may also include a “Reset Password” button 18J14 toenable a user to generate a new password. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18K is a sample of a user detail interface, consistent with oneembodiment of the present invention. The user detail interface includesuser information 18K02, including a user name 18K04, a user ID 18K06, auser e-mail address 18K08, and a user status 18K10. If the user detailinterface is used to edit an existing user, these fields will bepopulated with the saved user information. User status 18K10 may be, forexample, active or inactive. If the user ID is changed or if the statusis made active 18K12, employer application 402 will send a sign-ininformation e-mail to the user e-mail address when the record is saved.The user detail interface also includes user permissions for withholdingpayment and withholding profile 18K14, payment submission 18G16, andreports 18K18, e.g., transaction history report, withholding profilereport, and payment history report. The withholding payment andwithholding profile permission 18K14 may be represented by drop-downlists with the options of none, view and modify. These options indicatewhether a user is allowed to view or modify payments and/or paymentprofiles. The payment submission permission 18K16 may include adrop-down list with the options of none or submit to indicate whether ornot the user may submit payments. The report permissions 18K16 mayinclude a drop-down list of options such as “none” and “view” toindicate whether or not the user may view reports.

The user detail interface may include a “Cancel” button 18K20 that willabandon the user permissions detail interface and a “Reset Password”button 18K22 that will generate a new password and e-mail it to theuser's e-mail address 18K08. Finally, the user detail interface mayinclude a “Save” button 18K24 that stores the user details, for example,in user database 516. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 18L is a sample change password interface, consistent with oneembodiment of the present invention. The change password interface mayinclude a text box for an old password 18L02, a text box for a newpassword 18L04, and a confirm new password text box 18L06. Using thechange password interface, the user may be prompted to enter the newpassword twice. The change password interface may include a “Save”button 18L08 that will save the user's new password and e-mail thepassword to the user's e-mail account and a “Cancel” button 18L10 thatwill abandon the change password interface. It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 18M is a sample create payment home interface, consistent with oneembodiment of the present invention. The user is given an option tosubmit a payment in one of two ways: by using an existing paymentprofile or by creating a new one-time payment. If the user chooses tocreate a payment using an existing payment profile, the user may use adrop-down menu 18M02 containing the user's payment profiles to selectthe payment profile and then choose a “Continue” button 18M04. To viewthe payment profiles, the user may also select a “Payment Profile”button 18M06 that displays the payment profile home interface. Thecreate payment home interface also includes a payment list 18M08 thatcan be sorted by selecting one of the column headers, such as dateentered, profile name, effective date, or status.

The payment list 18M08 may be filtered by selecting a filter 18M10. Thefilter may include different options such as all, in progress, new, andsubmitted. Each entry in payment list 18M08 may be assigned to one ofthese options. “In progress” indicates that the payment profile is inthe processing stage. Profiles that have this status cannot be edited orcanceled. “New” indicates that the payment has yet to be processed, andprofiles that have a new status can be submitted, edited or canceled.“Submitted” indicates that the payment has been submitted forprocessing. Profiles that have this status can be edited or canceled upuntil the debit processing cutoff time. When a status option is selectedfrom filter drop-down list 18M10, the payment list will be refreshed todisplay only entries with the applicable status. If the status “all” isselected, then the payment list 18M08 will be displayed with allentries.

An action for each entry may be displayed through a number of actionbuttons on the create payment home interface. The buttons may include,for example, “S,” “E,” “C,” and “V.” The “S” button, for “submit,” mayenable a user to submit a payment prior to a debt processing cutofftime. The “E” button, for “edit”, may change the payment status to newand display a payment detail interface. If the request is made after thedebit processing cutoff time, the user will be prompted to accept a neweffective date. The “C” button, for “cancel,” will change the paymentstatus to cancel. This feature may not be available after the debitprocessing cutoff time. The “V” button, for “view,” may display thepayment detail interface in a read-only format.

The create payment interface payment list 18M08 may include a profilename 18M16, a date entered 18M18, and display options 18M20. Selecting aprofile name 18M16 displays the payment detail interface for theselected profile. Date entered 18M18 is based on when the user submitteda payment to the accumulator website. Display options 18M20 enable auser to select the number of entries in the payment list that aredisplayed at one time. The create payment interface may also include a“Previous” button 18M22 and a “Next” button 18M24 if the payment listcontains multiple pages to enable the user to navigate between themultiple pages. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 18N is a sample payment detail interface, consistent with oneembodiment of the present invention. The payment detail interfaceincludes a payment name 18N02 that may default to the payment profileselected from the create payment interface, an effective date 18N04, awithholding date 18N06, a bank account name 18N08, a number of employees18N10, and a total payment amount 18N12. The effective date 18N04 is thedate of the funds transfer from the employer's account to the recipient.The withholding date 18N06 is the date on which the funds are withheldfrom the employee's payroll. The bank account name 18N08 may default tothe default bank account saved in the employer's payment profile. Thenumber of employees 18N12 indicates the total number of employeesrelated to the profile, and the total payment amount 18N12 is the totalwithholding amount for all of the employees. The payment detailinterface may also include a “Cancel” button 18N16 to abandon thepayment detail interface and a “Continue” button 18N14 to save thepayment detail information. It should be noted that other embodimentsare possible, consistent with the present invention.

FIG. 18O is a sample employee list interface, consistent with oneembodiment of the present invention the present invention. On theemployee list interface, a user may select an “Add Employee” button18O02 to add an employee. The employee list interface may include anemployee identification number, such as a social security number 18O04and a case number 18O06. A “Delete Selected Employees” button 18O08enables the user to delete selected employees using check boxes 18O10.The employee list interface may also include a check box 18O12 to flagrecords where an employees has medical insurance. The employee listinterface also includes a withholding date 18O14 and a payment amount18O16, both of which may be drawn from a stored payment profile. Theemployee list interface may also include a “Previous” button 18O18 and a“Next” button 18O20 if the employee list contains multiple pages toenable the user to navigate between the multiple pages. The employeelist interface may also include a “Save Changes” button 18O22 that savesany changes made to the fields in the table and a “Continue” button18O24 that saves the employee list information and links to a paymentverification interface. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 18P is a sample payment verification interface, consistent with oneembodiment of the present invention. The payment verification interfaceincludes a profile name 18P02, an effective date 18P04, which may be thedate the recipient will receive funds, and a bank account name 18P06.The bank account name field may also display account information for thebank account including account type, account number, and routingtransmit number. The payment verification interface may also include anumber of employees 18P08 and a total payment amount 18P09. The data inthe payment verification interface may be read only for a user toconfirm the data entered in the payment detail interface. The paymentverification interface may include a “Cancel” button 18P10 that willabandon the interface without saving any payment information and a “MakeChanges” button 18P12 to enable a user to return to the payment detailinterface to make changes to the data. The payment verificationinterface may also include a “Save Payment” button 18P14 to save thepayment information and a “Submit Payment” button 18P16 to submit thepayment information, display a payment confirmation interface, and sendthe user a payment confirmation e-mail. The payment verificationinterface may also include a failure field 18P18 containing employeeswhose records do not pass the validation process performed when theemployee list is updated. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 18Q is a sample payment confirmation interface, consistent with oneembodiment of the present invention. The payment confirmation interfacemay include a customer service link 18Q02 to enable a user to contactthe web site's customer service as well as a reports link 18Q04 toenable the user to run reports. The confirmation interface may alsoinclude the date the payment was submitted 18Q06, a read only summary ofthe transaction 18Q08, and a “Return” button 18Q10. It should be notedthat other embodiments are possible, consistent with the presentinvention.

FIG. 18R is a sample payment profile list interface, consistent with oneembodiment of the present invention. Payment profiles are used by theemployer to create and submit withholding payments on a regular basis.The payment profile list interface may include an “Add Profile” button18R02 and a “Delete Selected Profiles” button 18R04. Selecting the “AddProfile” button 18R02 enables a user to add a payment profile using thepayment profile detail interface. The “Delete Profile” button 18R04 willdelete all payment profiles that are indicated by check boxes 18R08. Thepayment profile list interface includes a profile name 18R10, number ofemployees 18R12, and bank account name 18R06. A profile name link 18R10may link to the payment profile detail interface for the selectedprofile. The number of employees 18R12 may indicate the total number ofemployees in the payment profile. The payment profile list interface mayalso include a display options drop-down list 18R14, a previous button18R16, and a next button 18R18. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18S is a sample payment profile detail interface, consistent withone embodiment of the present invention. The payment profile detailinterface includes a payment profile name 18S02, a default bank accountdrop-down list 18S06, and a total payment amount 18S08. If an existingprofile exists, the payment profile name and default bank account fields18S10 are populated with the saved information. The payment profiledetail interface may also include a “Save and Update” button 18S12 torefresh the screen with updated bank account information and a “Cancel”button 18S14 to abandon the interface. The payment profile detailinterface may also include an employee list 18S16 with an employee name,social security number, state, case number, and payment amount. Theemployee list 18S16 may also include an “Add Employee” button 18S18 anda “Delete Selected Employees” button 18S20. The user may use check boxes18S22 to mark an employee for deletion when “Delete Selected Employees”button 18S20 is chosen. By selecting an employee name link 18S24, theemployee case detail interface for the selected employee is displayed.The payment profile detail interface may also include a display optiondrop-down list 18S26, a previous button 18S28, and a next button 18S30.It should be noted that other embodiments are possible, consistent withthe present invention.

FIG. 18T is a sample employee detail interface, consistent with oneembodiment of the present invention. Using this interface, the user mayenter and edit employee information as needed. The employee detailinterface includes an employee name 18T02, an employee social securitynumber 18T04, an employee state 18T06, an employee case number 18T08,and a FIPS number 18T09. Employee detail interface may also include anFIPS lookup button 18T10 that will open an FIPS lookup table interface.The employee detail interface may also include a withholding amount18T12, a radio button 18T14 to indicate whether the employee has medicalinsurance, and a check box for indicating whether the employee is nolonger employed 18T15. The employee detail interface may also include a“Cancel” button 18T16 to enable the user to abandon the employee detailinterface, a “Save” button 18T18 to validate the employee information,and an “Accept” button 18T20 to override the validation if it is notsuccessful. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 18U is a sample FIPS lookup table interface, consistent with oneembodiment of the present invention. This FIPS lookup table 18U02 may bespecific to a state corresponding to the employee and may be used todetermine the standardized county code corresponding to the employee.The state name 18U04 may be included in the heading of the FIPS lookuptable. The table may include a radio button 18U06 corresponding to eachFIPS code and county name. The FIPS lookup table may also include an“OK” button 18U08 and a “Cancel” button 18U10. If a state does not useindividual county FIPS codes 18U12, only one code may appear and thecounty code field may read “all counties.” Horizontal scrolling 18U14may be used to accommodate more counties than can be displayed on asingle interface. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 18V is a sample reports interface, consistent with one embodimentof the present invention. This interface enables a user to create andview reports. For a payment transaction report, the user may choose abeginning date range 18V02 and an ending date range 18V04 and thenselect a “Retrieve” button 18V06 to open a window with a paymenttransaction report. To display a payment profile report, a user mayselect a profile name from a drop-down list 18V08 or select to view allpayment profiles. When a user selects a “Retrieve” button 18V10, apayment profile report is displayed. To display an employee paymenthistory report, the user is prompted to enter a social security number18V12 and a date range 18V13. By selecting a “Retrieve” button 18V14,the user is presented with a payment history report for that employee.It should be noted that other embodiments are possible, consistent withthe present invention.

FIG. 18W is a sample payment transaction report, consistent with oneembodiment of the present invention. The report will display allsubmitted payment profiles 18W04 within the specified date range 18W02.

FIG. 18X is a sample payment profile report, consistent with oneembodiment of the present invention. This report displays all paymentprofiles selected by the user 18X02. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 18Y is a sample employee payment history report, consistent withone embodiment of the present invention. This report indicates theemployees selected by the user 18Y02 as well as the date range selectedby the user 18Y04 and shows all payments for the employee during thattime. It should be noted that other embodiments are possible, consistentwith the present invention.

FIG. 19 is a flow chart of processing performed by administratorapplication 404 consistent with one embodiment of the present invention.An administrator at accumulator 104 may use administrator application404 to assist an employer accessing accumulator 104 via employerapplication 402 to submit electronic payments consistent with thepresent invention. As shown in FIG. 19, the administrator may selectfrom several options using administrator application 404. These optionsmay be presented, for example, as buttons on a graphical user interface.

If the administrator selects user permissions (step 1902), thenadministrator application 404 implements a user permissions updateprocedure (step 1904). The user permissions update procedure isexplained below with reference to FIG. 20. If the administrator selectscompany information update (step 1906), then administrator application404 implements a company information update procedure (step 1908). Thecompany information update procedure is explained below with referenceto FIG. 21. If the administrator selects bank account information update(step 1910), then administrator application 404 implements a bankaccount information update procedure (step 1912). The bank accountinformation update procedure is explained below with reference to FIG.22. If the user selects returns handling (step 1914), then administratorapplication 404 implements a returns handling procedure (step 1916). Thereturns handling procedure is explained below with reference to FIGS.23A and 23B. If the user selects credit batch handling (step 1918), thenadministrator application 404 implements a credit batch handlingprocedure (step 1920). The credit batch handling procedure is describedbelow with reference to FIG. 24. Finally, if the administrator selectsbatch processing (step 1922), then administrator application 404implements a batch processing procedure (step 1924). The batchprocessing procedure is described below with reference to FIG. 25. Itshould be noted that other embodiments are possible, consistent with thepresent invention.

FIG. 20 is a flow chart of an embodiment of a user permissions updateprocedure, consistent with one embodiment of the present invention.Using this process, administrator application 404 enables anadministrator to edit the permissions of one or more users.Administrator application 404 displays a user list interface (step2002), and the administrator selects a user ID (step 2004). As describedabove, FIG. 18J includes a sample user list interface consistent withthe present invention. The user list may include, for example, a userID, user name, and status for one or more users authorized to accessaccumulator 104 on behalf of employer 102. When the administratorselects a user ID (step 2004), a user detail interface is displayed(step 2006). As discussed above, FIG. 18K includes a sample user detailinterface. The administrator may enter or edit user permissions, forexample, user name, status, user type, e-mail, and user ID and selectsave (step 2008). Administrator application 404 then saves the userinformation to, for example, user database 516 (step 2010). An updateduser list interface is displayed (step 2012) and a sign in informatione-mail is sent to the user's e-mail address (step 2014). It should benoted that other embodiments are possible, consistent with the presentinvention.

FIG. 21 is a flow chart of an embodiment of a company information updateprocedure, consistent one embodiment of with the present invention.Using this process, administrator application 404 enables anadministrator to update company information. First, a company searchinterface may be displayed (step 2102). FIG. 26B contains a samplecompany search interface. When the administrator enters searchinformation, such as a FEIN number or company name, the administratorchooses search to locate the appropriate company (step 2104).Administrator application 404 queries the company directory, stored forexample, in registration database 512 (step 2106) and displays a companylist interface corresponding to the company queried (step 2108). FIG.26A includes a sample company list interface. From the company listinterface, the administrator may select the appropriate company bychoosing a FEIN number text link (step 2110). Administrator application404 displays a company detail interface for the selected company (step2112). FIG. 26C contains a sample company detail interface. Theadministrator may make edits to the company information using thecompany detail interface and choose save (step 2114). Administratorapplication 404 then saves the company detail information in, forexample, registration database 512 (step 2116). It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 22 is a flow chart of an embodiment of a bank account informationupdate procedure, consistent with one embodiment of the presentinvention. Using this process, administrator application 404 enables anadministrator to edit bank account information. First, a bank accountlist interface is displayed (step 2204). FIG. 26D includes a sample bankaccount list interface. The administrator may select a bank name (step2206), and the bank account detail interface for the selected bank isdisplayed (step 2208). FIG. 26E includes a sample bank account detailinterface. On the bank account detail interface, the administrator mayselect reactivate (step 2210) to instruct the administrator application404 to update the bank account status to “reactivated” in the databasewhere the bank account detail information is stored (step 2212). Theinformation may be stored, for example, in registration database 512 orpayment database 504. When a bank account is reactivated in this way,the administrator application 404 will hold the next payment for thatbank account for ten days (step 2214) and then remove the bank accountfrom the return reason bank account list (step 2216). In this way, anadministrator may allow an employer to begin using a bank account afterthe account has been rendered inactive due to, for example, a paymentreturned by the bank for insufficient funds. The administratorapplication 404 then displays an updated bank account list interface(step 2218). It should be noted that other embodiments are possible,consistent with the present invention.

FIGS. 23A and 23B are flow charts of an embodiment of a returns handlingprocedure, consistent with one embodiment of the present invention.Using this process, administrator application 404 enables anadministrator at accumulator 104 to handle returned payments. A returnedpayment may occur, for example, when an employer submits a payment froman account that does not have a sufficient balance to process the debitor from an account that has been closed. The bank may return the paymentunprocessed and marked, for example, return for insufficient funds. Toprocess such a return, administrator application 404 displays a returnsinterface (step 2302). FIG. 26F includes a sample returns interface.When the administrator at accumulator 104 enters a query, such as anaccount number or an effective date, and chooses search (step 2304),administrator application 404 searches for a corresponding batch listand displays a bank account information on the returns interface (step2306). The administrator is prompted to select a reason for returnusing, for example, a reason for return code, select the applicable bankaccount, and choose update (step 2308). Administrator application 404will change the status of the selected bank account to “inactive” andstore the selected reason for return code with the related batch (step2310). This will cancel all future payments associated with the selectedbank account (step 2312). The bank account information may be copied byadministrator application 404 to a returned reason code bank accounthistory table (step 2314). A disable company interface will be displayedcontaining all employers that have the same bank account (step 2316).FIG. 26G includes a sample disable company interface. The administratorat accumulator 104 may indicate a company to disable and choose update(step 2318). An inactive bank account notification e-mail will be sentto all employers using that bank account (step 2320), and the returnsinterface will be displayed (step 2322). It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 24 is a flowchart of an embodiment of a credit batch handlingprocedure, consistent with one embodiment of the present invention.Using this process, administrator application 404 enables anadministrator to perform credit batch handling. A credit batch may be,for example, a collection of credits to be submitted in one batch.First, a batch status interface is displayed (step 2402). FIG. 26Hincludes a sample batch status interface. An administrator may enter aquery, such as an effective date or a batch number, and choose search(step 2404). Administrator application 404 then locates and displaysrecords matching the query (step 2406). These records may be located bysearching, for example, payment database 504. When an administratorchooses “Release Credit” (step 2408), administrator application 404 setsa credit batch effective date to the current date plus an effective datevariable (step 2410). The effective date variable may be, for example,three days, to allow for any returns from the employer's bank to bereceived before any corresponding credits are released to the recipient.Next, an updated batch status interface is displayed (step 2412).Batches of debits may also be handled in this way. It should be notedthat other embodiments are possible, consistent with the presentinvention.

FIG. 25 is a flowchart of an embodiment of a batch processing procedure,consistent with one embodiment of the present invention. Using thisprocess, administrator application 404 enables an administrator ataccumulator 104 to process either debits or credits in a batch. A batchinformation interface is displayed (step 2502) and the administrator mayselect one of several options. FIG. 26I includes a sample batchinformation interface. If the user selects “View Batch Detail” (step2506), then a batch detail interface is displayed (step 2508). If theadministrator selects “Recreate” (step 2510), then administratorapplication 404 recreates the batch file (step 2512), sends the batchfile to the appropriate bank (step 2516), and displays an updated batchinformation interface. If the administrator selects “Resend” (step2514), then administrator application 404 sends the batch file to theappropriate bank (step 2516) and displays an updated batch informationinterface (step 2518). It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 26A is a sample company list interface, consistent with oneembodiment of the present invention. This interface enables anadministrator using administrator application 404 to view a list ofcompanies registered to access accumulator 104. The company list 26A02may contain all companies matching a user's search criteria. For eachcompany in the list, the interface may include an account number, FEINnumber, a company name, and a company status 26A04. The company listinterface may also include a “Delete Selected Companies” button 26A06that will delete all company details for a company selected by theadministrator. The company list interface may include a checkbox 26A08for each company listed that may be checked to indicate that theadministrator wishes the company to be deleted. The company listinterface may also include a display option drop-down list 26A10 thatenables the administrator to choose the number of companies displayed onthe list at any one time. The company list interface may also include a“Previous” button 26A12 and a “Next” button 26A14 if the company listcontains multiple pages to enable the administrator to navigate betweenthe several pages. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 26B is a sample company search interface, consistent with oneembodiment of the present invention. This interface enables anadministrator using administrator application 404 to search for one ormore companies meeting designated criteria. To find company detail, theadministrator is prompted to enter search criteria, such as a FEINnumber, a company name, an account number, or a user ID. The companysearch interface may include a drop-down box 26B02 to show theadministrator the options of search criteria. Once the user selects oneof these options from drop-down box 26B02, the user may enter theappropriate data in a text box 26B04. The format of text box 26B04 maybe dictated by the selection of drop-down list 26B02. The company searchinterface may also include a filter by status drop-down list 26B06 ofoptions such as all, active, inactive over 180 days, new, orinsufficient funds. Finally, the company search interface may include asearch button 26B08 to activate the administrator application's searchfor the company matching the query information. It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 26C is a sample company detail interface, consistent with oneembodiment of the present invention. This interface enables anadministrator using administrator application 404 to edit companydetails as necessary and save any changes made. The company detailinterface includes instructions to the administrator 26C02 and a “ViewBank List” button 26C04 to display a bank account list interface. Thecompany detail interface may also include a status of the company and/ora primary user 26C06. These status fields may be depicted as drop-downboxes with options such as active and inactive. If the status isinactive, a read-only inactive reason 26C08 may be displayed for thecompany, for example, NSF for insufficient funds. Other read-onlyinformation may be included in company detail interface 26C10 including,for example, account number, FEIN, company name, company address, andzip code. If the primary user's status is inactive, a read-only inactivereason may be displayed 26C12, such as sign-in failure. The primary userportion of the company detail interface may also include a primary username 26C14, primary user phone number 26C16, user ID 26C18, and e-mailaddress 26C20. It should be noted that other embodiments are possible,consistent with the present invention.

All of the fields 26C22 may be prepopulated with information stored, forexample, in registration database 512 or user database 516. The primaryuser field 26C24 may be editable by the administrator. The companydetail interface may also include a “Cancel” button 26C26 to abandon theinterface and a “Save” button 26C28 to save the company detailinformation. If the company status has been changed to inactive, areason of “inactivated by administrator” will be stored in companystatus inactive reason 26C08. If the user status has been changed toinactive, the user status inactive reason 26C12 will be set to“inactivated by administrator.” If the primary user's status is changedto active, the system will generate a new password for the primary userand send an account information e-mail to a primary user. It should benoted that other embodiments are possible, consistent with the presentinvention.

FIG. 26D is a sample bank account list interface, consistent with oneembodiment of the present invention. The bank account list 26D02 mayindicate the company name 26D04 corresponding to the bank list beingviewed. This interface enables an administrator to view or edit bankdetail by selecting one of the accounts on the bank account list 26D08.The bank account list interface may include a “View Company Detail”button 26D06 that displays the respective company detail interface forthe company selected. The bank account list 26D08 may include a bankname, routing transit number, account number, and account type. In thebank account list interface, selecting one of the column headers maysort the bank list by the data in that column. The bank name text links26D10 may display a bank account detail interface for the selected bankaccount. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 26E is a sample bank account detail interface, consistent with oneembodiment of the present invention. The bank account detail interfaceincludes data about a selected bank account 26E02, such as bank name,account number, account type, routing transit number, maximum withdrawalamount, status, and reason. The bank account detail interface may alsoinclude a reactivate button 26E04 to update the status of the bankaccount to reactivate it and place the next payment request on the10-day hold process as described above in reference to FIG. 22. The bankaccount detail interface may also include a “Cancel” button 26E06 toreturn the user to the bank account list interface of FIG. 26D. Itshould be noted that other embodiments are possible, consistent with thepresent invention.

FIG. 26F is a sample returns interface, consistent with one embodimentof the present invention. The returns interface includes a bank accountsearch portion 26F01 and a bank/company information portion 26F03. Bankaccount search portion 26F01 of the returns handling interface enablesan administrator to find a bank account using a routing number and/orother bank account numbers. Bank account search portion 26F01 includes aset of fields such as account number and routing number 26E02, effectivedate 26F04, and state 26F06. The effective date may be, for example, thedate that the return happened at the reporting bank. The bank accountsearch portion may also include a drop-down list 26F06 of all of thestates and a “Search” button 26F08 that will match the entered routingnumber, bank account number, and effective date to the batch list forthe selected state.

Bank/company information portion 26F03 of the returns interface mayinclude a drop-down list 26F10 containing all of the return reason codeswith their descriptions. For example, return code 01 may indicateinsufficient funds. The bank/company information portion may alsoinclude a table 26F12 that depicts search results based on the searchcriteria entered in bank account search portion 26F01 of the returnsinterface. The search results may include a bank name 26F14 and acheckbox 26F16 to indicate what bank account will be updated with aselected return reason code from drop-down list 26F10. The bank/companyinformation search results may also include an amount field 26F18 todisplay the payment amount for the related batch and a state field 26F20that displays the state where the batch was sent. The search results mayalso include a bank name 26F22, an account number 26F24, a batch number26F26, and an effective date 26F28. A company name field 26F30 maydisplay the company name that is associated with the bank account fromthe search results. The company name may be provided as a link that willdisplay the company details interface for the selected company. Thebank/company information portion may also include an “Update” button26F32 that will change the bank account status to “inactive” and storethe selected return reason code, canceling any related payments anddisplaying a disable company interface. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 26G is a sample disable company interface, consistent with oneembodiment of the present invention. The disable company interface mayindicate a company to be disabled due to, for example, a predeterminednumber of returned payments. Disabling a company will lock it out of theaccumulator. The disable company interface includes bank accountinformation 26G02 selected from the returns interface. The bank accountinformation may include, for example, a bank name, batch number, state,account number, effective date, and payment amount. The disable companyinterface also includes a company information list 26G04 all of thecompanies with the same bank account number. Company information list26G04 may include a company name 26G08, a primary user 26G10, a phonenumber for the primary user 26G14, and a checkbox 26G12 where theadministrator may indicate that the company selected is to be disabled.The company information list may include column headings 26G06 that canbe used to sort the list by the data in that column. The disable companyinterface may also include an “Update” button 26G16. Choosing the“Update” button will post a notice of inactive bank account for allcompanies listed and send an inactive bank account notification to aprimary user for each of the companies listed. It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 26H is a sample batch status interface, consistent with oneembodiment of the present invention. To locate a batch, theadministrator may enter search criteria and choose “search.” Batchesmatching the search criteria will be listed on the batch statusinterface. The search criteria may be entered in a find results portionof the batch status interface, including a batch number 26H02, aneffective date 26H04, a batch type 26H08, and a state 26H10. The batchtype 26H08 may include a drop-down list for the administrator toindicate whether the batch is a debit batch or a credit batch. The statefield 26H10 may include a drop-down list containing all states. Thebatch status interface may also include a display option 26H14 to enablethe administrator to determine how many batches are listed in the batchlist portion of the batch status interface. The batch status interfacemay also include a “Previous” button and a “Next” button 26H16 if thelist contains multiple pages to enable the administrator to navigateamong the multiple pages.

The batch list portion 26H30 of the batch status interface includes aneffective date 26H18 of the payments in the batch, a batch number 26H20,a batch status indicator 26H22, a batch amount 26H24, a bank status26H26, and a state 26H28. Batch number 26H20 may be a unique number forthe batch. The batch number 26H20 may be a text link to the batchinformation interface for the selected batch. The batch status 26H22 mayindicate what type of batch it is, for example, a debit batch or acredit batch. The batch amount 26H24 is the total amount of dollars inthe batch. The bank status 26H26 indicates whether the batch containsnew bank accounts or established bank accounts. The state 26H28indicates what recipient the batch is for. The batch status interfacemay also include action buttons 26H32 to indicate the next appropriateaction for the batch. For example, the buttons may include a “ReleaseCredit” button 26H32 or a “Close Batch” button 26H32. Choosing the“Release Credit” button initiates credit batch processing. This may onlybe available when the debit processing has been completed. Choosing“Close Batch” closes the batch. This may only be available after thecredit processing has been completed. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 26I is a sample batch information interface, consistent with oneembodiment of the present invention. The batch information interface mayinclude a batch number 26I02, an effective date 26I04, a batch creationdate 26I06, a batch status 26I08, a batch stage 26I10, and a bankaccount type 26I12. The batch number 26I02 may be a unique number forthe batch. The effective date 26I04 may be the effective date (i.e., thedate of delivery to the recipient) of the payments in the batch. Thebatch creation date 26I06 may be the date the batch was created. Thebatch status 26I08 indicates if the batch is active or not. The batchstage 26I10 indicates where the batch is in its lifecycle (e.g., debitprocessing, credit processing, etc.). The bank account type 26I12indicates whether the bank account corresponding to the batch is new orestablished. The batch information interface may also includeinformation about a debit and a credit corresponding to the batch.

The debit information may include a debit bank 26I14 indicating the bankthe file was sent to for debit processing, a number of employers 26I16in the batch, and a number of employer payments 26I18. The debitinformation may also include a debit file creation date 26I20 indicatingthe date the file was created, a debit file send date 26I22, indicatingthe date the debit was sent to the bank for debit processing, and adebit file amount 26I24 including the sum of the employer payments inthe batch file. The debit portion may also include a button for “ViewDebit Detail” 26I24 that displays the debit batch detail interfacecorresponding to this batch, a “Recreate and Resend File” button 26I26enabling a system administrator to recreate and resend the debit batch,and a “Resend File” button 26I30 that enables the system administratorto resend the debit batch to the bank.

The credit information may include information similar to the debitinformation, including a credit bank, number of employers, number ofemployer payments, credit file create date, credit file send date, andcredit file amount. The credit information may also include a “ViewCredit Detail” button 26I28 to display the credit batch detail interfacefor the corresponding credit batch as well as a “Recreate and ResendFile” button and a “Resend File” button. The batch information interfacemay also include a “Return to Batch Status” button 26I32 that enablesthe administrator to return to the batch status interface of FIG. 26H.It should be noted that other embodiments are possible, consistent withthe present invention.

FIG. 26J is a sample debit batch information interface, consistent withone embodiment of the present invention. The debit batch informationinterface may include a batch number 26J02 that may be a unique numbercorresponding to the batch, an original effective date 26J04 listing theeffective date of the payments in the batch, and a batch creation date26J06 containing the date the batch job was created. The debit batchdetail interface may also include a batch status field 26J08 to indicatewhether the batch is active, a batch stage field 26J10 to indicate wherethe batch is in its lifecycle, and a bank account type 26J12 to indicatewhether the bank account is new or established. The debit batch detailinterface may also include debit bank information 26J14, a number ofemployers 26J16, and a number of employer payments 26J17. The debitbatch detail interface may include a debit file creation date 26J18, adebit file send date 26J20, and a debit file amount 26J22.

The debit batch detail interface may also include a list 26J24 of thedebits in this batch. The list 26J24 of debits may include a state 26J26indicating where the payment was sent, a company name 26J28 displayingthe company name associated with the payment, a bank name 26J30displaying the bank name for the payment, an account number 26J32, andan amount field 26J34. In addition, the debit batch detail interface mayinclude a display option drop-down list 26J36 to enable an administratorto determine how many debits are displayed at one time. The debit batchdetail interface may also include a “Previous” button 26J38 and a “Next”button to enable an administrator to navigate between multiple pages ofthe debit batch list. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 26K is a sample credit batch detail interface, consistent with oneembodiment of the present invention. The credit batch detail interfacemay include a batch number 26K02, an effective date 26K04, a batchcreation date 26K06, batch status 26K08, and bank account type 26K10.For the credit batch, the credit batch detail interface may also includecredit bank information 26K12, a number of employers 26K14, a number ofemployer payments 26K16, a credit file creation date 26K18, a creditfile send date 26K20, and a credit file amount 26K22. The credit batchdetail interface may also include a list 26K24 of the credits in theselected credit batch. The credit batch list may include the state wherethe credit file was sent 26K26, the company name 26K28, an employee namefor the payment being made 26K30, a case number corresponding to thepayment of the employee 26K32, and an amount of the associated payment26K36. The credit batch detail interface may also include a button 26K34to enable the administrator to return to the batch informationinterface. The interface may also include a display option drop-downlist 26K38 to enable an administrator to determine how many credits aredisplayed at one time, a “Previous” button 26K40, and a “Next” button.It should be noted that other embodiments are possible, consistent withthe present invention.

FIG. 26L is a sample reports menu, consistent with one embodiment of thepresent invention. This menu may be presented to an administrator at theaccumulator 104 via administrator application 404. The reports menu mayenable an administrator to run a number of reports, including a batchsummary report, a payment submittal report, an SDU credit summaryreport, and an employer payment returns report. It should be noted thatother embodiments are possible, consistent with the present invention.

FIG. 26M is a sample batch summary report, consistent with oneembodiment of the present invention. A batch summary report may be usedto view and print the status of selected batch groups. An administratorcan view batch summaries by state, by date range, by specific employer,or by all employers. The batch summary report may include the date andtime on which it is run, the state for which it is run, the query startdate, and a query end date. The batch summary report may include a batchnumber, a number of employers, a batch type, an effective date, a debitdate, a debit value, a credit date, the returns before the credit, thecredit value, returns after the credit is processed, and a batch status.The batch summary report may also include a totals column to total thedebit value, credit value, and returns before and/or after the credit isissued. The batch summary report may include a print button to enablethe administrator to print the batch summary report. It should be notedthat other embodiments are possible, consistent with the presentinvention.

FIG. 26N is a sample payment submittal summary report, consistent withone embodiment of the present invention. This report provides asummarized view of payments submitted by an employer or by all employersfor a specific date range in a specific state. The submittal summaryreport includes the state, the start date, the end date, and theemployer. The report contains values for the employer submittal date,requested effective date, actual effective date, employer name, bankaccount status, number of employee records, total amount of employerpayment, and batch status. It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 26O is a sample SDU credit submittal summary report, consistentwith one embodiment of the present invention. This report presents asummarized view of credit payments sent to a specific state's SDU withina specific submittal date range. The SDU credit submittal summary reportincludes a date the credit was submitted to the SDU, a state, a reportdate, a starting submittal date, and an ending submittal date. The datashown on the SDU credit submittal summary report may include, forexample, a date the payment was submitted to the SDU, a number ofemployer records, the number of employee records, and a credit value.The SDU credit submittal summary report may also include a print buttonto enable the administrator to print the SDU credit submittal summaryreport. It should be noted that other embodiments are possible,consistent with the present invention.

FIG. 26P is a sample employer payment returns report, consistent withone embodiment of the present invention. This report presents asummarized view of returns on payments made by employers for a specificdate range for a specific state. The employer payment returns report mayinclude the name of an employer, the report run date and time, thestate, and the return date range. The data in the employer paymentreturns report may include, for example, an employer name, the employerID or account number, the batch number, the return date, the amount ofthe returns pre-credit, the amount of the returns post-credit, thereturn reason, the contact name, the phone number, and an extension ofthe employer's primary contact. The employer payment returns report mayalso include a print button to enable the administrator to print theemployer payment returns report. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 27 is a block diagram of an alternative embodiment of a system forprocessing payments to multiple states, consistent with the presentinvention. As shown in FIG. 27, an employer 102 communicates withaccumulator 104 to register and to submit payments. The accumulatoragency submits files to SDU 110 where a payment processor 2702 and adelivery module 2704 are used to process payments to a plurality ofstates 2706. In another alternative embodiment, payment processor 2702and delivery module 2704 may be part of accumulator 104. It should benoted that other embodiments are possible, consistent with the presentinvention.

FIG. 28 is a block diagram of another embodiment of a system forprocessing payments to multiple states, consistent with the presentinvention. Employer 102 submits payments to a payment database 504 ataccumulator 104. Payment database 504 has access to payment profiles2802 which may be stored, for example, in profile database 510 (notshown). Payment database 504 also has access to templates 2804. Thesetemplates may be different for each of the plurality of states 2806.Delivery module 408 accesses payment database 504 and templates 2804 tocreate payments and deliver them to for a plurality of states 2806.

For example, in FIG. 28, two states, Michigan and Illinois, may receivepayments from Employer 102. A national employer 102 with employees inthese two states and one weekly payroll may have one payment profilethat includes both Michigan and Illinois employees, as opposed to havingtwo weekly profiles, one for Michigan and one for Illinois. Employer 102may access accumulator 104 to create a single payment profile for all ofits weekly employees and to enter data for each employee such as theemployee name and Federal Information Processing Service (FIPS) code.Payment database 504 may retrieve the appropriate template associatedwith a particular state, e.g., Michigan, to filter the data from thepayment profile to match Michigan's specification. Payment database 504may use another template, e.g., for Illinois, to filter the data tomatch Illinois's specifications. Accumulator 104 may generate a singledebit for the employer but send multiple credits, e.g., one for Michiganand one for Illinois. Likewise, the employer may provide one set of datawhile accumulator 104 may filter and/or format the data differentlybefore sending it to each state. It should be noted that otherembodiments are possible, consistent with the present invention.

FIG. 29 depicts a series of templates, consistent with one embodiment ofthe present invention. A national template 2902 may be used to gatherinformation from an employer. In this way, an employer completes onlyone template of information regardless of the number of states to whichthe employers' payments will ultimately be routed. Accumulator 104 maymaintain a series of state templates 2904 corresponding to each statethat receives payments from accumulator 104. After an employer completesthe information required by national template 2902, accumulator agency104 may filter the information from the national template to create dataand a payment for each state based on state templates 2904. In this way,the employer enters only one set of information which is then used tocreate the state specific information required by individual states(e.g., individual SDUs). It should be noted that other embodiments arepossible, consistent with the present invention.

FIG. 30 shows a plurality of delivery methods at an accumulator,consistent with one embodiment of the present invention. As shown inFIG. 30, a plurality of states 2904 may receive data and payments fromdelivery module 408 in a plurality of different ways. For example,State₁ may receive electronic data, State₂ may receive electronic fundstransfer, and State_(n) may receive paper. In this way, an employer maysubmit payment information to accumulator 104 for a plurality of states2904 without knowing the specific delivery requirements of eachindividual state. The delivery requirements for a state may be stored,for example, in its state template 2904. It should be noted that otherembodiments are possible, consistent with the present invention.

Other embodiments of the invention will be apparent to those skilled inthe art from consideration of the specification and practice of theinvention disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the invention being indicated by the following claims.

1.-42. (canceled)
 43. A method for processing a payment at anaccumulator over a network, comprising: receiving employer informationfrom an employer via the network; storing the employer information;receiving employee information corresponding to an employee from theemployer via the network; storing the employee information; verifyingthe employee information using verification information received from anintermediary; and when the employee information is verified, creating apayment corresponding to the employee information, submitting thepayment to a financial clearinghouse via the network, and storing datarelated to the payment.
 44. The method of claim 43, wherein the employerinformation includes at least one of user information and employeraccount information.
 45. The method of claim 43, wherein the submittingfurther includes: processing a debit to the financial clearinghouse, thedebit to be applied against an account of the employer.
 46. The methodof claim 45, wherein the submitting further includes: receiving a creditfrom the financial clearinghouse, the credit to be applied to an accountof the intermediary.
 47. The method of claim 45, wherein the debit isprocessed using debit-based electronic funds transfer.
 48. The method ofclaim 46, wherein the credit is processed using addendum-basedelectronic data interchange.
 49. The method of claim 43, wherein theemployee information relates to a child support payment.
 50. The methodof claim 43, further including: generating a report based on theemployee information.
 51. The method of claim 50, further including:sending the report based on the employee information to the employer.52.-58. (canceled)
 59. A system for processing a payment at anaccumulator over a network, comprising: a first receiving componentconfigured to receive employer information from an employer via thenetwork; a first storing component configured to store the employerinformation; a second receiving component configured to receive employeeinformation corresponding to an employee from the employer via thenetwork; a second storing component configured to store the employeeinformation; a verifying component configured to verify the employeeinformation using verification information received from anintermediary; and when the employee information is verified, a creatingcomponent configured to create a payment corresponding to the employeeinformation, a submitting component configured to the payment to afinancial clearinghouse via the network, and a third storing componentconfigured to store data related to the payment.
 60. The system of claim59, wherein the employer information includes at least one of userinformation and employer account information.
 61. The system of claim59, wherein the submitting component further includes: a processingcomponent configured to process a debit to the financial clearinghouse,the debit to be applied against an account of the employer.
 62. Thesystem of claim 61, wherein the submitting component further includes: athird receiving component configured to receive a credit from thefinancial clearinghouse, the credit to be applied to an account of theintermediary.
 63. The system of claim 61, wherein the debit is processedusing debit-based electronic funds transfer.
 64. The system of claim 62,wherein the credit is processed using addendum-based electronic datainterchange.
 65. (canceled)
 66. The system of claim 59, furtherincluding: a first generating component configured to generate a reportbased on the employee information.
 67. The system of claim 66, furtherincluding: a first sending component configured to send the report basedon the employee information to the employer.
 68. The system of claim 59,further including: a second generating component configured to generatea report based on the employer information.
 69. The system of claim 68,further including: a second sending component configured to send thereport based on the employer information to the employer. 70.-74.(canceled)
 75. A computer readable medium having computer readable codeembodied therein for processing a payment at an accumulator over anetwork, the computer readable code comprising: a first receiving moduleconfigured to receive employer information from an employer via thenetwork; a first storing module configured to store the employerinformation; a second receiving module configured to receive employeeinformation corresponding to an employee from the employer via thenetwork; a second storing module configured to store the employeeinformation; a verifying module configured to verify the employeeinformation using verification information received from anintermediary; and when the employee information is verified, a creatingmodule configured to create a payment corresponding to the employeeinformation, a submitting module configured to submit the payment to afinancial clearinghouse via the network, and a third storing moduleconfigured to store data related to the payment. 76.-266. (canceled)